[regression] - Exported files don't honor the module assembly settings

I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691

Unfortunately, it seems a regression has crept in, because using the same projects attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of sarproject.sar, when earproject is deployed on (any) JBoss AS.

In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The resulting org.eclipse.wst.common.component contains :

<project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="sarproject">
        <wb-resource deploy-path="/" source-path="/src"/>
        <dependent-module archiveName="junit.jar" deploy-path="/" handle="module:/classpath/var/JUNIT_HOME/junit.jar">
            <dependency-type>uses</dependency-type>
        </dependent-module>
    </wb-module>
</project-modules>

-earproject : needed so sarproject can be a Module project. I've manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed. Here is the end result :

<project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="earproject">
        <wb-resource deploy-path="/" source-path="/EarContent"/>
        <dependent-module archiveName="sarproject.sar" deploy-path="/" handle="module:/resource/sarproject/sarproject">
            <dependency-type>uses</dependency-type>
        </dependent-module>
    </wb-module>
</project-modules>