Today we had an ASP.NET worker process chew up 100% of the CPU on both our Web servers.  In the course of trying to diagnose the problem someone asked a simple question: how can you tell what Web App that worker process is associated with so we can flog the developer?  Can anybody tell me how you would go about tracking down the associated Web App for an ASP.NET worker process?  I quashed the idea to flog the developer... it's just not in the spirit of ISO 9001.