Hi Mark
Not sure...
Do you know the component is in memory because memory hasn't been released?
In which case you could check that the destroy event happens and use it to explicitly clean up. This should really be in the deactivate event in case you do start pooling.
From memory, (pardon the pun) there were memory leaks in EAServer version 10 years ago. A very small part of a component could take up lost space, eventually leaving only smaller and smaller chunks free, ultimately causing decline in performance and failure.
Do you know the component is in memory because Jag Manager tells you after you have refreshed to folder?
Lars