Here's a sample Maven project that demonstrates the problem with 4 classes. Just run 'mvn clean test'.

But how's the parent bean injection working in the original question, the one that contains @Produces?

Answer to q1 is yes, though not full blown EJB jar, just CDI.

It'll be a few days before I can answer q2. I'm in day 1 of a 2000 mile cross-country drive.

you're right, ear is the intended format though for now, I'm deploying as war. The module that's expecting the list to be injected is a web module with a dependency on the CDI jar module.

BTW, how do I enable Weld debug logs when testing in Arquillian?

Sorry for the late response, as I said, I was on the road.

The bean discovery mode for the CDI jar module is ALL.

I'm using an Arquillian managed Wildfly that's downloaded by the maven-dependency-plugin for every build. It'd be difficult to automatically modify the standalone.xml for it. I guess I could work out a hack to copy a modified standalone.xml to the download location.

That said, it occurred to me that perhaps we should look at how the CDI jar is loaded into Arquillian to make sure that's right to begin with. I'm loading the dependency from the pom and I'm not sure there's anything in it that tells Arquillian to consider the beans.xml from that project. 

@Deployment

    public static WebArchive createDeployment() throws FileNotFoundException {

  File[] hospitalUser = Maven.configureResolver().workOffline()

  .withMavenCentralRepo(false).withClassPathResolution(true)

  .loadPomFromFile(new File("pom.xml"))

  .resolve(HOSPITAL_USER_MVN_COORD).withTransitivity().asFile();

  WebArchive app = create(WebArchive.class, SERVICE_NAME + ".war")

  .addPackages(true, Filters.exclude(".*Test.*"),

  AvailabilityApp.class.getPackage())

  .addAsWebInfResource(

  new File(WEB_APP_PATH, "WEB-INF/beans.xml"))

  .addAsLibraries(hospitalUser);

  System.out.println(app.toString(true));

  return app;

}