This is fixed.

(my email repsonse to the problem)
My unit tests were checking the return code, but didn't take the extra step of seeing that the members were still members. I changed the unit test so it now fails, and I see what the issue is... it seems if you add a Subject object to a Set, and then see if the subject is in Set, it will always return false since this Subject doesn't override the equals()/hashcode() methods. So I will change it so it doesn't use a set... will be fixed in 1.4.1 which will come out soon.

Lets test with replacing but with a delete and an add, and check the resulting list completely instead of hasMember... just to make sure all bases are covered...