ThreadNameValidationTest fails if run alone (or first in suite)

This seems to happen because code that configures Log4j logging system triggers creation of a thread factory after the test saves the count of created thread factories, so the test thinks that there is some production code doing so, even though it's an artifact of our test code.