Can we still use loader-repository to scope deployments and override server classes in EAP 5?

Issue

• If we find a conflict between the jars present in an ear and those in the as, is it a valid solution to use the following type of configuration in jboss-app.xml discussed here:

    <jboss-app>
      <loader-repository> 
      com.example:archive=unique-archive-name 
         <loader-repository-config> 
         java2ParentDelegation=false 
         </loader-repository-config> 
      </loader-repository>
    </jboss-app>