Major Description
While looking into a hang (unsure if it's related) I found that there were two "Log4j2-TF-AsyncLogger[context]-*" threads running.
We end up re-initializing the logger internally when a Disruptor instance is created because it also requests a logger. It doesn't appear as though this results in an incorrect background thread ID, but the intermediate thread is leaked.
