thanks for the quick response.
This blog entry and the linked KB entry is exactly what I needed. I will check this and modify my policies, since my company is kind of bound to XP and Server 2003 R2.
I will see how the memory leaks are going when the settings have been made and report back, so that if anyone comes up with the same issue, he can find the solution.
OK. I have made the changes like you have described in McAfee KnowledgeBase - Non-page pool memory leak on Windows Server 2003 with VirusScan 8.8 installed and the issue has greatly improved.
Thank you very much for sharing that piece of information.