JMX registration of Recoverer fails when multiple serverIds are used

When running two separate web application that use Spring configured BTM instances on the same Tomcat instance, the following exception is thrown at startup:

Caused by: javax.management.InstanceAlreadyExistsException: bitronix.tm:type=Recoverer
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
... 111 more

This is thrown by ManagementRegistrar.register("bitronix.tm:type=Recoverer", this); in the constructor of Recoverer
when the second web application starts.

I'm using the following Spring configuration in each web application with different server ids:

<bean id="btmConfig" factory-method="getConfiguration" class="bitronix.tm.TransactionManagerServices">

<property name="serverId" value="$

-btm1.tlog" />
<property name="logPart2Filename" value="$

-btm2.tlog" />
<!-- <property name="disableJmx" value="true"/> -->

</bean>

<bean id="jtaTransactionManager" factory-method="getTransactionManager"
class="bitronix.tm.TransactionManagerServices" depends-on="btmConfig" destroy-method="shutdown" />

If I set disableJmx to true then there are no exceptions (as expected). Just wonder if there is a way to configure the JMX registration to allow two instances of BTM to use the same JMX server.