Revision 1741908

Revert breaking changes to protected api.  The changes to RemoteEvent's were originally made to ensure safe publication of remote events, while debugging race conditions.  It was suspected that the sequence id of RemoteEvent's were being read as their default value, causing the event to be ignored.  RemoteEvent's can still be published safely, by ensuring a reference to the RemoteEvent, is final, volatile, or a value in a concurrent collection, or read while synchronized or using a lock.