Circular EJB dependencies shouldn't be a problem. What exactly does the code look like?
The problem is that Wildfly checks for valid EJB dependencies on deployment. Can you turn that option off? If you have circular EJB dependencies, you can't ever deploy the two projects unless you could somehow deploy them simultaneously
So these 2 EJBs are part of 2 different top level deployments? If not, then it shouldn't fail. The EJB spec allows circular dependencies within the application.
Anyway, there isn't any config option to disable skipping these kind of dependencies. More details about your application packaging and the EJBs might help us understand the deployment better and maybe someone can then suggest a solution or workaround.