Fix for JERSEY-1813: Wrong handling method is used for EJB business interface methods in GF
 - unified test launching for apps needing standalone GF container

Change-Id: I2ea19caaa80f8d000041570d8acd47fc3f138202
JERSEY-1630: Jersey should not log warning when exception cannot be mapped to a response

 - changed logging level of unmapped exceptions to FINE
 - updated JerseyTest to set level of loggers to the specified values

Change-Id: I83a82f877fd1314c649ea68610e8bda34ec97f23
Resolved JERSEY-1669.

- Template pushing in the routing fixed ("Path params do not work correctly with ambiguous templates." fixed).
- PS2: Minor optimizations (Marek+Mira)
  - matched template pushing algorithm + updated javadoc
  - multiple RuntimeModelBuilder router creation

Change-Id: Ic775eaa408f02660092d4d2abc737932b271131c
Merge "JERSEY-1630: Jersey should not log warning when exception cannot be mapped to a response"
Merge "Resolved JERSEY-1669."