Broker: default - Client: xxxx.xxx already connected from

Issue

As in,
http://fusesource.com/issues/browse/ESB-1345

One of our bundles has a durable subscriber. Everytime we redeploy we get the following errors (in loop) until we restart the whole ESB. This does not seem to be an acceptable way to deploy a bundle. How can this be resolved?

2013-05-13 16:32:58,605 | WARN  | c.businessevent] | faultJmsMessageListenerContainer | 143 - org.springframework.jms - 3.0.7.RELEASE | Could not refresh JMS Connection for destination 'com.example.businessevent' - retrying in 5000 ms. Cause: Broker: default - Client: mamintegration.nqcbusevent already connected from tcp://10.40.199.90:39664
2013-05-13 16:33:03,613 | WARN  | c.businessevent] | faultJmsMessageListenerContainer | 143 - org.springframework.jms - 3.0.7.RELEASE | Could not refresh JMS Connection for destination 'com.example.businessevent' - retrying in 5000 ms. Cause: Setting clientID on a used Connection is not allowed
2013-05-13 16:33:08,622 | WARN  | c.businessevent] | faultJmsMessageListenerContainer | 143 - org.springframework.jms - 3.0.7.RELEASE | Could not refresh JMS Connection for destination 'com.example.businessevent' - retrying in 5000 ms. Cause: Setting clientID on a used Connection is not allowed