Impact of EJBs in other EJBs' Manifest.mf

We have a (Maven) project, running on wildfly, where there are a lot of dependencies within the EJBs where A depends on B and C, B depends on C.

In order to clean up the POMs and make automatic structure analysis easier the dependencies were changed from provided to compile in order to take advantage of the transitive dependencies. Allowing us to define the dependencies in the POMs as A->B & B->C.

This has the side effect of including all the EJBs the artifact depends on in the class-path of the manifest.mf.

This leaves the question: Does having the EJBs, that are usually exposed by wildfly to each-other, in the manifest class path have any undesirable effects or potential current or future problems?