First problem - deployment.
What does your deployment descriptor look like?
Second problem - sharing violation
This is a known problem with windows and the jdk's jar
file entry caching.
it looks to me as if you are deploying your package twice: once throught the ant jmx task, and then again by copying it into the jboss deploy directory and waiting for the autodeployer. This is apt to have somewhat unfortunate results, although I'm somewhat surprised that _all_ the mbeans don't appear. Personally I like to use the ant jmx task to deploy stuff during development since it doesn't clutter up the jboss deploy dir and if I restart the server I have a clean slate.