Edit: I think I've misread your question when answering this - I'll leave the answer here just in case somebody else finds this question and has some static content requirements different from yours. Peter and Miguel give answers that better match your specific question)
An easy way might be to leverage liferays cdn features (cdn="Content Delivery Network"). Unfortunately - on a quick scan through the documentation - I've only found this configuration option but missed some information about what content is considered "static". That's not to say that the information isn't there - I just didn't find it.
I guess that - even though a cdn implies a different hostname - you might get away with the same host name and possibly another webapplication context path (e.g. the path on your server). You can deploy any number of independent applications within the server serving liferay.
Especially when you want to single out static content to a different host/application, you might be better of with a dedicated server (or at least dns name) or the apache/tomcat conbination, as apache reportedly serves static content with a lot less resources than tomcat does.