Under certain conditions, the ActivationGroup will forcibly unexport itself in
the midst of servicing a remote call which may cause the VM to exit before
the call returns.

One particular example is that if the first object activated in an
ActivationGroup fails, the ActivationGroup will unexport itself, potentially
causing the VM to exit before the "newInstance" call returns. In
the finally clause of ActivationGroupImpl.newInstance, the checkInactiveGroup
call will result in the ActivationGroup being forcibly unexported since
there will be no objects in the activation group if the first activation
in the group fails.

The ActivationGroup should not forcibly unexport itself while executing a
remote call. Also, the VM should not exit while remote calls are pending or
are in progress (see 4308492).