Killing remote bridge end results in unrecoverable SuspectExceptions

During sync replication testing, I killed the backup site's bridge end connection. Subsequent writes were unable to continue.

See logs at:

http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/xsite_syncKillCoord/10.30.12.156/server.log.gz
http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/xsite_syncKillCoord/10.30.12.157/server.log.gz
http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/xsite_syncKillCoord/10.30.12.158/server.log.gz

{den-dg1 (10.30.12.156), den-dg-2 (10.30.12.157), and den-dg3 (10.30.12.158)}

were backups for another cluster. The node den-dg2 was the RELAY2 coordinator. It was then killed. The cluster processed the view change, but the newly elected coordinator kept broadcasting commands to include den-dg2. For instance:

2012-09-26 15:09:49,123 TRACE [org.infinispan.remoting.rpc.RpcManagerImpl] (Incoming-10,erm-bridge,_den-dg3-27305:den) den-dg3-27305(den) broadcasting call PrepareCommand {modifications=[PutKeyValueCommand

{key=8a93b36d-9519-4886-9527-115b8394ec90, value=..., flags=[IGNORE_RETURN_VALUES, SKIP_XSITE_BACKUP], putIfAbsent=false, lifespanMillis=-1, maxIdleTimeMillis=-1}

], onePhaseCommit=false, gtx=GlobalTransaction:<den-dg3-27305(den)>:196:local, cacheName='ermSession', topologyId=4} to recipient list [den-dg2-7712(den), den-dg3-27305(den)]