Marto's suggestion to migrate to Test::Selenium::Remote::Driver could be elegantly done by writing your own module Test::WWW::Selenium::Bridge that copies the API of the old module and maps the calls to wrap the new one.

Like this you'd only have to append ::Bridge to all your uses of Test::WWW::Selenium in your "fairly substantial, but 'old', set of tests"

This should be not too hard if you are really ...

> My tests all take the form of

... only using 3 methods + new.

Disclaimer: I never used Selenium. Here might meet be dragons or other road bumps.

But even if it's more complicated, this strategy should give you quick results and reduce your migration risks.