You probably just want LWP and one of the HTML munging modules (probably HTML::TreeBuilder). You can reduce your resource usage somewhat by:

• remembering to free up after you're done with a parsed tree ($tree->delete, to break any reference cycles)
• take advantage of Mason's caching if possible (which will use more local disk and/or RAM depending on what Cache::Cache setup you're configured to use, but will require less processing and network traffic if you can avoid another LWP fetch and parse)

If you're really worried, you might write a separate custom proxy using HTTP::Proxy or POE and then use apache's mod_proxy to make those results appear under your server's URI namespace.