Here is a link to our agency blog that discusses how we were able to identify memory leaks in our BlogEngine.net 1.6.1 platform, map the runaway worker process using PID matching to the web application configuration in IIS, and then repair it by implementing proper static constructors in the code.

http://www.fuzionagency.com/post/2010/12/15/SEO-Expert-Jared-Nielsen-Troubleshoots-Memory-Leak-Errors-in-BlogEnginenet-161-and-IIS-7.aspx