It does seem odd that the w3wp.exe process would grow to be that large. Usually this indicates a memory leak in some web application on that website.
You could set up the application pool to recycle itself after it consumes a specific amount of memory. This will keep exchange from freezing up. Although it doesnt fix the root of the problem itself, it just masks the symptoms temporarily.
Do your users use the outlook thick client, or OWA?