Okay. I'm just a bit nervous about calling another framework from within a constructor since we can't control the chain of events. I'll merge for now, and we can revisit if necessary. A quick scan through the code shows that there are indeed some questionable things going on... but from what I've seen, I'm actually more concerned about the AbstractServer constructor calling newClient(..) where there is at least one case in Curator itself of allowing an instance to escape during its own constructor:

```
public CuratorFrameworkImpl(CuratorFrameworkFactory.Builder builder)
{
    ...
    failedDeleteManager = new FailedDeleteManager(this);
    namespaceFacadeCache = new NamespaceFacadeCache(this);
}
```