Yes, the version of code you are running seems to exhibit the behavior you are experiencing in very large environments. A restart of the services will take care of the resource issue. Then once restarted the process will grow and grow over time. So you may get into situations where you have to restart the service every now and then. As I mentioned this issue is usually due to large environments with a lot going on. Splitting up your schedules, segmenting your environment, leveling the playing field will help to alleviate the additional load on the process. Or, you could just upgrade to 5.x and the problem will go away all together. That was my experience anyways. I know 'upgrade' isnt the best answer, but I do know that it will solve your problem.