Safer handling of mbean registration

In test env, this fails often in tests (with loud logs).

Simple change to unregister before registration if already exists.

Though opened pull here to see if anyone else has issues with the components in the test-env are only getting lifecycle operations (dispose in this case) once per-test-class... which is the root cause of this problem.

ie. this could be a symptom of a larger problem.