Memory leak on the GroupWise client can arise due to the applet calling the Object API in a sequence which leads to the API state becoming unstable.
Our experience with the GroupWise APIs has taught us that sometimes an obvious or intuitive approach is not feasible; that an applet must be redesigned to work around an API defect or to manage internal API resources.
The difficulty is usually in figuring out which API is responsible for the problem. Using the process of elimination, however, you can usually narrow the problem down rather quickly by making small logical changes and observing the impact on the problem. The key is to make only one change at a time and then see if the problem goes away. You can use the Trace commands to your source code to get a real-time picture of the execution sequence. See the Developers Guide section Error Handling and Debugging for details.
Hope this helps.