The solution section first describes the main solution. For most patterns, there is more than one way to realize it. We document these different ways as strategies. Of course, as the usage of these patterns spreads as we have seen since they went live, people may realize these patterns in other ways currently not documented in the patterns. Looking at it another way, strategies allow us to evolve the patterns as people develop newer implementations.
Web based applications probably get the best bang from the patterns.
However, you bring up an excellent issue. We think that one of the best benefits of the catalog is not only looking at the individual pattern, but looking at how many are used in conjunction. The Service Locator pattern includes strategies that are related to JMS and lookups. I think that may provide you some direction for what you are looking for. It is something others have brought up.