Have a look at the method java.sql.DriverManager#getConnection where the exception is thrown, it seems that it's one of 2 possibilities:
the driver did not register itself. Modern drivers register themselves automatically when their class is loaded
The driver registered itself, but it's not visible by the classloader of the caller and so it get's skipped.
I would suggest to put some breakpoints on java.sql.DriverManager#getConnection and in java.sql.DriverManager#registerDriver to see what is going on.
What is strange is why was it working before. Usually we should put the driver in $TOMCAT_HOME/lib, see this post. There it is always visible to any part of the application and prevents registering drivers multiple times.
Try to remove the driver from the WAR and make sure it's in $TOMCAT_HOME/lib. If it doesn't work you can always edit the question with further findings, hope it helps.