This doeesn't look possible now. It may be worth filing an improvement jira for.
But I'm trying to understand what you're trying to do a little better. So you intentionally have each thread create a new unique pool when its submits a job? So that pool will just get the default pool configuration, and you will see lots of these messages in your logs?
What is the use case for creating pools this way?
Also if I understand correctly, it doesn't even matter if the thread dies -- that pool will still stay around, as the rootPool will retain a reference to its (the pools aren't really actually tied to specific threads).