Non-project EJB dependencies should not be placed in the .modulemaps file

If I have an ear project that depends on an ejb artifact that was previously built (ie, it's not another project in my multi-module pom), the plugin should not put an entry for that artifact in the .modulemaps file. It should (and currently does) put an entry in application.xml.

If there is an entry in .modulemaps, RAD gets confused and displays the following error:

IWAE0027W The project OPFCommonServices for module or utility JAR OPFCommonServices.jar in enterprise application project BP does not exist in the workspace.

In this case, OPFCommonServices.jar is an artifact that was built previously but is an EJB library in my enterprise application.