Well, that would sound nice, but the scanner used by our config is set to using 'org.jboss.deployment.scanner.PrefixDeploymentSorter'. When Jboss is deploying the custom deploy directory, it isn't using it. Any other suggestions? Is there a way to prevent the custom deploy directory from being added? That way I could manually add the deploy directory and that would work.