I am seeing a container injected "jsessionid" matrix parameter interfering with my router's ability to match resources (good!). I'm pretty sure it is related to the container managed security encountering a request that has no "jsessionid" cookie; either way it has no meaning to Restlet (I would think the same behavior would come from disabling cookie based session tracking). Since the session handling is specific to the Servlet spec, I think it would make sense for the ServletAdapter.toRequest method to chomp the "jsessionid" if it appears in the request's resource reference.