Alright. I've got this working with the maven-assembly-plugin as my workaround. I am deploying to JBoss and so far this is working for me.
Basically, in your POM you want to to include the following:
<!-- include dependencies in manifest classpath -->
<!-- utilize maven assembly plugin to include dependency jars for standalone ejb-jar deployment -->
Then, you'll have to create a directory called $
/src/assembly and in there create a file named assembly.xml with the following:
<?xml version="1.0" encoding="UTF-8"?>
<!-- for some reason the assembly plugin includes the actual jar for the project which causes JBoss to
try and register the EJB twice. we exclude it here so that we don't run into this error on startup/redeploy -->
<!-- include the code for the EJB -->
I still think the plugin should be fixed, but I hope this helps people. If the plugin isn't going to be fixed, then perhaps this info should be posted to the site so that people are aware of a workaround for this feature.