remove1.js doesn't wait for the shunned secondary to fully realize its removal from the cluster before it gets added back in. If the system is slow enough to let this actually happen, the test fails:
http://buildlogs.mongodb.org/Windows%2064-bit/builds/5448/test/replica%20sets/remove1.js