By hostile I mean that the legacy system had no API, was implemented using obfuscated code, and resisted being driven by URLs.
We needed to integrate with it to create documents, calendar appointments, etc. in the legacy system, based on stuff that was happening in the newer system we were building.
We ended up using PhantomJS to implement a module that drove the legacy system via its HTML user interface -- pushing buttons, selecting meeting participants from the HTML select tags, submitting forms, etc.
Although that sounds (and is!) hacky as hell, it worked flawlessly 100% of the time. PhantomJS was a gift from the gods.
But that's one use case where I would love to use phantomJS or any other headless engine to test the frontend. I'm aware that for headless testing to work, there should be a headless browser of every major vendor. Maybe it's an utopia.
Being able to use websockets in my automated testing has been something of a holy grail, so jquerygo and phantomjs have been hugely helpful.
Edit: it appears to be WebKit 538.1, from May 2014. But this is based on a readme which is pretty old, so it could be outdated info
For PhantomJS 2.0, I think they ship with a version of webkit that is > 6 months old.
If you use casperjs you can modify the executable (it's python) and change "'default_exec' : 'slimerjs'" into "'default_exec' : 'xvfb-run slimerjs'"