The component war (inside the component ear) tries to bind MetricsService to JNDI in MetricsJNDIPublisher. This then allows Hservices code to lookup MetricsService and use it to make calls into the java api. It is currently used by the backfiller set avails when feeds go down.
I believe this worked at some point in the past, perhaps because we were deploying as a war before, or maybe just on an earlier WildFly, but it is not working now, inside the ear.
The general mechanism used in metrics a combo of @ApplicationScoped and @Eager. This results in a failure binding to jndi, either because we're trying to it is application scoped, or because of the extension nature of Eager:
...Caused by: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only