Just wanted to chime in… the latest version (0.9.6) of eAccelerator removes all manual page caching functions (such as eaccelerator_get and eaccelerator_put).
From this point forward, unless someone else commits to updating and maintaining that component of eAccelerator, the developer has stated the feature will likely not be returning. He is focusing only on the opCode caching component of the software and cutting out all extra features.
It seems eAccelerator is not a good option for page caching in W3TC as of the newest releases.