memory leak in DLL

Hello,

I've posted to this list previously about memory leaks in JAWIN.  We are
using JAWIN in an app server that pools threads.  We discovered we needed to
turn off JAWIN's COMObjReleaser as threads were holding onto COM references
if they slept for any period of time.

I've profiled our app server using YourKit and jawin.jar no longer leaks
memory as I call close() on every single object that's produced -- running
the application standalone for a few hours shows JVM heap usage to be constant.

However memory usage of the process still climbs leading me to believe
jawin.dll is the culprit.  To narrow the result I wrote a C# class that
calls into the native C++ library we use jawin.dll to access.  It does not
leak memory, however the same code in Java causes the process to use upward
of 1.5GB of VM space before it gets killed.

Is there an easy way to profile heap usage of jawin.dll?

A pecularity of my code is that a call into a COM object will return another
COM object.  Could this scenario cause jawin.dll to leak?