Background:

tomcat-juli.jar is really just a repackaged version of apache-commons-logging.  By default Tomcat (6 and 7) ships with a reduced version of tomcat-juli.jar that is hard-coded to use java.util.logging.  Therefore you cannot configure Tomcat to utilize Log4J.  (This does not include web applications; they can configure log4j separately.)

Tomcat provides the "full" version of tomcat-juli.jar as an extra download, along with tomcat-juli-adapters.jar.  Both jars are necessary to enable Tomcat to utilize Log4J.

Problem:

EWS 1.0.x shipped with the "full" version of tomcat-juli.jar by default and tomcat-juli-adapters.jar was found in the "extras" folder.  EWS 2.0.0 shipped with the reduced version of tomcat-juli.jar and did not include tomcat-juli-adapters.jar, therefore preventing Tomcat from utilizing Log4J in a supported manner.  This is a loss of functionality between EWS 1 and 2, further exposed by EWS 2.0.0 documentation explaining how to configure Tomcat to utilize Log4J when it's not possible (without downloading unsupported jars from the tc7 website).

Solution:

Either include the "full" tomcat-juli.jar as the default implementation or provide it in the "extras" folder along with tomcat-juli-adapters.jar.  This should be done for both tomcat 6 and 7.