Dropping the artifactory.war  in v3's autodeploy directory triggers the following scan error documented at http://forums.java.net/jive/thread.jspa?
This is a case of an application being forced to use Jersey 1.1 bundled in GlassFish v3 instead of the 1.0 library that it ships with.
Even with class loader delegation set to false Jersey 1.0 will look in META-INF/services of jersey installed in GF.
Of course it would be nice to have Jersey 1.0 apps run unmodified on 1.1 but only strict adherence to the JAX-RS specification offers compatibility
between 1.0 and 1.1 releases.
Removing jersey from the GFv3 distro sounds like a bad solution (glassfish-management depends on it).
An application should be able to ship and use its own set of libraries with some sort of "ignore system/GlassFish libraries" isolation at deploy time.