Those are warnings rather than errors. I'm not sure what the cause of the first one is. There is no use of Java Faces in WQS. Could it be your Tomcat config?
The second is Spring grumbling because the setBaseUrl operation on the WebScriptCallerImpl class comes in two flavours: one that accepts a String object and one that accepts a URI object. Spring is able to auto-convert a property value from String to URI and from URI to String, so it's just indicating that it's picking one of the options (the one that takes a String).
The third is odd - you shouldn't be seeing it, and I don't see it when I run WQS here. It suggests that the file "ehcache.xml" is missing from the WQS sample webapp. That file should be in the WEB-INF/classes directory of the wcmqs WAR file. I'll double-check the latest build and fix it if I see the problem.