Mocking equals results in next test failing also

We are using EasyMock (and ClassExtensions) in our test framework. A co-worker tried to mock equals (I later told him that was not neccessary) and got some funny results. Not only his actual test failed, the next executed test also failed. EasyMock seems to remember that there was a aborted recording and doesn't reset its state.
Attached are examples for EasyMock and Class Extensions.

Thank you and best regards
Marcel Freese