See parent issue for basic problem description. This subtask is for when total replication is used and region based marshalling is not configured.

Need to think about this one a bit more. Here the cache might remain active after webapp undeploy, and will remain consistent with the cluster. When the webapp starts, it doesn't do a state transfer (cache already did a full transfer when it started), so it can't remove local state and then transfer.

Need to determine if we want to support a concept of letting a cache that's the first one to start (e.g. after a full cluster restart) go ahead and read persistent state. Or, do we simply set the cache's cache loader's "purgeOnStartup" to true and flush persistent state. With the latter, the persistent store is purely used for passivation overflow and not for HA; HA is provided by the cluster. But no state survives a complete cluster restart.