We are working on functionality to allow files to be deployed to a file system, but in the meantime I suggest that you place your binaries in a particular section ("/images", for example), and configure a reverse proxy cache in front of your JEE web container (Tomcat, for instance) with appropriate caching config on that path.
In my spare time I am also working on a more intelligent caching mechanism that will cache binaries in the web tier but automatically detect when a cached entity needs to be refreshed. Similar to what is done with the asset metadata and asset collections.
