Aware IM has been extensively tested for memory leaks. It is unlikely that this is the problem. Of course, we cannot rule out the leaks completely - there might be some rarely used operation that causes a leak. But it is still unlikely.
The fact that the memory is not released is not an indication of a leak, but could be an indication of a problem in your application - that's why you need to monitor it. You have to understand that Aware IM provides a framework but a lot depends on the application itself - this relates to both memory usage and performance.
Now Codrin's utility performs some magic at the operating system level - as a result it improves the performance of the Java garbage collector. The fact that it successfully cleans up memory indicates that Aware IM itself does not have a problem (otherwise, memory wouldn't have been released), but the operating system may not work as efficiently as it could. So the utility can be very useful as Codrin says.
It is possible that the utility will solve George's problem if it is indeed caused by the operating system. But it is also possible that it won't - if the problem is caused by the application itself.
