The problem turned out to be that I had a Phantom script called webpage.js in the directory from which I was trying to execute my Casper scripts. I suspect that Casper's patched version of Phantom's loader was mistaking this for the Phantom webpage module.
The co-incidence of names makes this an event unlikely to occur for other people. But if it does, merely renaming the offending script should deal with the problem, and I'd recommend treating all entries in the casperjs/bin/casperjs
file's native_args list as reserved words.