Following a support call done by @ecarmona
The problem was a clash of requests through localhost via port 8093, which is the SSL port in Pulse.
An environment in Pulse was set to use port 8093 to connect to the monitor where Pulse was installed.
This caused Pulse to generate a request to its own Web Server SSL port, a request that never finished.
The solution was to temporarily disable port 8093 in the server.xml of Pulse and change the environment settings to use port 8094 instead of 8093.