Since you already have the context, would you have a problem in caching the "context path" value in a variable or some form of a constant/hash-map and access that in your beans or business service layer. I don't think that did be difficult if you are not changing that variable/path - which in spring MVC/servlets - you will never need to!
On the other hand is there a trouble that I am not seeing in as to why you cannot cache the context path in a "String" and access it later where-ever you need?
Other things you can do is have a bean conveniently encapsulate the ApplicationContext and pass it down your call heirarchy into the business layer as a parameter.
Java Pal - Your friend in technology and innovation...India.