What happens when the exception is thrown? It propagates up the stack, effectively popping stack frames, until it reaches the main method again where it is caught. You should have just as much space on the stack before you call go(), as after you call it.
When any exception happens, the virtual machine searches the stack for active exception handlers (compatible catch blocks), unwinding the stack in the process. When your exception handler in the main() method is found, the stack is already nearly empty (only the main method is on the stack, apart perhaps from some of the VM bootstrap methods); all the go() calls were already removed.
Try modifying your test to handle the exception in the go() method itself - that way the exception handler will be found and executed when the stack is still full. If you call another method from the exception handler, chances are you'll get another StackOverflowException. You'll have to craft the test very carefully to get a good image of what is going on, as an exception in the catch block will mask the original exception that caused the catch block to be executed. Therefore calling System.out methods to log things up will probably cause the stack to overflow again, preventing you from displaying all the exceptions that have occurred.