Original jarfile is kept open in exploded EAR

SourceForge Submitter: koreth .
This happens with both 3.2.1 and 3.2.2.

The attached zipfile contains an exploded .ear
directory with a utility jarfile at the top level. The
.war directory's manifest references the utility
jarfile in its manifest classpath.

JBoss makes a copy of the utility jarfile, but it seems
to not close the original file, which means that on
Windows it's impossible to delete or rename the .ear
directory when I want to redeploy the application. On
UNIX that's not an issue since you can delete open files.

Running Process Explorer (an lsof-like tool for
Windows, see www.sysinternals.com) confirms that JBoss
has open file handles on both its temporary copy of the
utility jarfile and the original.

If I use a file rather than an exploded directory for
my .ear, I can redeploy to my heart's content, but I'd
really rather use an exploded directory (easier to
update JSPs at runtime, etc.)

To reproduce, unpack the zipfile into a running
server's deploy directory on a Windows box, wait a few
seconds for it to deploy, and then try to delete the
.ear directory. You'll get a "file is in use" error.