Deployments deployed by the jboss.ha:service=HASingletonDeployer use always the default class loader repository. The reason is that the deploy-hasingleton directory is deployed by the jboss.system:service=MainDeployer MBean. The Main deployer delegated this work to a JarDeployer that uses the default class loader repository. All deployments in this directory are subdeployments with the same class loader repository.

As a workaround the jboss.deployment:type=DeploymentScanner,flavor=URL could be used. This scanner scans the directory instead of creating a jar deployer. The workaround works only, if the ScanEnabled property of the jboss.deployment:type=DeploymentScanner,flavor=URL is not set to false.