Restricting system resources to .NET application

I am maintaining a managed Windows Service project which basically invoke/run the (managed) jobs (IJob implementations from different sub-teams) at scheduled time. There are few jobs which occasionally stall the system resources.

While waiting for my sub-teams to debug/fix their jobs, is there any way that I can somehow control in my parent executor before it happens…for instance starting multiple AppDomain开发者_运维百科s and then somehow restricting system resources (CPU, memory, number of managed threads the job can spawn etc) allowed to each AppDomain? Can Windows Activation Service (Windows 2008) help if we host the jobs as WCF and invoke them through WAS?

There's an article on CodeProject which shows how you could restrict the memory used by a given process.