Verifier failing due to UCL scope

SourceForge Submitter: oravecz .
I have two ear files, EAR1 and EAR2 and both contain
EJB1 and EJB2 respectively. EJB2 makes a call to EJB1,
and to facilitate this call EJB2 contains the classes it
needs to access EJB1. These classes include the Home
and Remote interfaces and any objects used as
parameters or return values. These classes are also
bundled in EAR1 since it needs these files to deploy and
execute.

This is a typicial setup for us, and the EARs are
packaged according to J2EE standards, and deployed in
this manner with jBoss 2.4.6. I am now deploying to
jBoss 3.2.2RC2, and I am getting errors from the
container. The errors are caused by the new UCL. The
workaround is to remove duplicate classes from the two
EAR files, but this should not be necessary.

Steps
==============================
1. Deploy the two EAR files. All of the classes are part of
the same UCL repository since we do not specify any
scoping using jboss-app.xml. Because the same class
cannot appear multiple times in the repository, the
server gives us warning regarding duplicate classes at
deployment time. This is expected behavior and
shouldn't affect the runtime usage of our beans.

2. However, the Verifier complains:

Warning: The methods defined in the remote interface
must have a matching method in the Bean's class with
the same return type.

Perhaps there is a bug in the Verifier?

3. Even though the verifier failed, setting the
EJBDeployer's StrictVerifier to false allows the beans to
deploy, and the unit tests execute properly.