This has to be a bug.

I'm seeing the same problem here. One of my WAR's dependent JARs contains EJBs and an ejb-jar.xml. Even though the dependent JAR is not listed as a module in application.xml the JBoss deployer is deploying it (again).

Does anyone know how to stop the deployer doing this?

Thanks, Matt

3.0 was changed to support more complicated packaging.
Looking the the code,

/**
* This method returns true if the name is a recognized archive file.
* This can be overridden for alternate behaviour.
*
* @param name The "short-name" of the URL. It will have any trailing '/'
* characters removed, and any directory structure has been removed.
* @param url The full url.
*
* @return true iff the name ends in a known archive extension: jar, sar,
* ear, rar, zip, wsr, war, or if the name matches the native
* library conventions.
*/
protected boolean isDeployable(String name, URL url)
{
return name.endsWith(".jar")
|| name.endsWith(".sar")
|| name.endsWith(".ear")
|| name.endsWith(".rar")
|| name.endsWith(".zip")
|| name.endsWith(".wsr")
|| name.endsWith(".war")
|| (name.endsWith(nativeSuffix) && name.startsWith(nativePrefix));
}

Changing the suffix will stop it deploying, but
I can't guarantee the behaviour won't change again.

Perhaps you should raise a bug or feature request
at www.sf.net/projects/jboss

Or maybe you can put the jars somewhere else
and configure the url for the jars using a
resource-ref?

Regards,
Adrian

> Perhaps you should raise a bug or feature request
> at www.sf.net/projects/jboss

Looks like it's already been raised, http://sourceforge.net/tracker/index.php?func=detail&aid=589808&group_id=22866&atid=376685.