Tests using a component manager rule fail when using Surefire's parallel mode

JUnit tests can be executed in parallel mode, with either suites, classes, or individual methods being distributed to one of the threads. When using components, mock expectations set for a test might interfere with the code being executed for another test. To (nondeterministically) try to reproduce the problem, simply add this for the surefire plugin configuration:

            <parallel>classesAndMethods</parallel>
            <threadCount>2</threadCount>

It fails even with the weaker option <parallel>suites</parallel>.

Being able to run tests in multiple threads would greatly speed up the build time.