Camel Jetty Thread Pool disappears from the JMX view if other than default settings are used

If a jetty component is configured as a bean in camel-blueprint or spring with default thread pool settings, the thread pool is visible in the JMX tree under org.eclipse.jetty.util.thread/queuedthreadpool. If threadpool settings are added (either by creating a separate thread pool bean or by changing the available settings on the jetty component), the threadpool is no longer visible in the JMX tree.

Dumping the server via the JMX dump operation reveals that the settings have taken effect, but the threadpool bean itself does not appear to be registered with the server.

I have tried various approaches to force registration of the threadpool (commented out in attached blueprint example) with no success.