steps:
Screencast: https://youtu.be/XMA--S9zj6s

1. EXEC: create an application (via ex. nodejs-mongo-persistent template)
2. ASSERT: pod for service is running
3. EXEC: select pod and pick "Port Forwarding..." and start the forwarding
4. ASSERT: forwarding is running
5. EXEC: verify on the cmd-line that the forwarding is running

   $ ps ax | grep oc
   47793   ??  S      0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
   

6. EXEC: in Explorer: select the pod for your service and pick "Delete"
7. ASSERT: pod gets deleted and recreated
8. EXEC: verify on the cmd-line that the forwarding is running

   $ ps ax | grep oc
   47793   ??  S      0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
   

Result:
The port forwarding is still running.
In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is NOT running, since we're asking about port-forwarding for the new pod (not the old one that was killed).

PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.