There are no patches attached to issue #7600 so I'll assume you are referring to my patches for issue #7060.
The problem I intended to address is:
1) new JarFile( ... )
2) no finally clause that closes the jarFile
3) file stays locked until gc kicks in so problems can occur when you undeploy/redeploy the app.
I'm not sure how this qualifies as a memory leak, btw.
Also I'm not sure how keeping references to the entries of the jar come in play. For the problem I had, the stream does not need to be closed while its entries are still in use. I would assume all references to the entries are nullified somewhere during undeploy.
Regards,
Dies
[Message sent by forum member 'dkoper' (diesk_at_fast.au.fujitsu.com)]
http://forums.java.net/jive/thread.jspa?messageID=361915