Two instances of using ObjectInputStream that may not have visibility into application classloader

This is basically the same issue as the previously opened OWB-464. Both InstanceImpl and EventImpl use an ObjectInputStream that will not have visibility into Application classes in a tiered classloading environment.

Will tentatively fix this the same way, by adding an extra layer of ObjectInputStream wrapping with a customer OIS that has the overwritten resolveClass method.