You can modify the rule above to match all of those paths using a "local OR" in the RewriteRule pattern, and back-referencing the entire path:
RewriteCond %{HTTP_HOST} ^store\.example\.com
RewriteRule ^((.+\.(html?|css|js))|images/[^.+]\.(gif|jpe?g|png))$ http://www.example.com/$1 [R=301,L]
Be aware of a very important point. Do not rely on this code to "make your site work," because these redirects force the visitor's browser to make two requests for every page and object they try to fetch. This slows down your site (which Google now measures) and it makes a mess of your logs and tracking data -- every request is doubled. Instead, be sure your pages themselves link to the proper URLs and use this code only to speed up the replacement of old incorrect URLs in search engines.
Redirects cannot be used as a "quick fix" to correct basic on-page linking errors.
Be very sure that you understand the effects of these redirects on your site's performance, ranking, and maintainability and on the validity or your 'stats' for traffic analysis...
Another point that you bring up: Apache .htaccess code affects only HTTP requests. It will have no effect on 'file includes' that reference only the local filesystem. Therefore, if you are doing a 'file include' on mm_menu.js, you will need to be copy that file or symlink it into the correct fileapace, because .htaccess cannot fix this problem. If instead you are linking to that file in a <script> tag, then use a server-relative (starts with a slash and the full server filepath) or an absolute URL, instead of trying to use a page-relative URL-path.
[added] Some good tutorials, references, and examples are cited in our Apache Forum Charter, and in our Apache Forum Library. See the links at the top of this page. [/added]
Jim