RAC & Failsafe :: Why Sessions Are Not Disconnected After Service Reallocation

i have 2 nodes RAC with service piodbserv2 which is active only on 2nd node. client is connected for (100% sure) to piodbserv2 on node2. i am doing relocation of this service to node1 using -f (force) option:

[oracle@rac1 ~]$ srvctl relocate service -d piodb -s piodbserv2 -i piodb2 -t piodb1 -f
[oracle@rac1 ~]$ srvctl start service -d piodb -s piodbserv2 -i piodb1
PRKP-1064 : Service piodbserv2 is already running on instance piodb1.
[oracle@rac1 ~]$ srvctl start service -d piodb -s piodbserv2 -i piodb2

-f (force) option is described as this which forcibly rellocate users from one to another node simply disconnecting sessions from node2 in my example

but i am surprised because my session is still opened on node2 after piodbserv2 relocation

SQL> select sys_context('userenv','instance') from dual;

SYS_CONTEXT('USERENV','INSTANCE')
-------------------------------------------------------------

2

SQL> select sys_context('userenv','instance') from dual;

SYS_CONTEXT('USERENV','INSTANCE')
-------------------------------------------------------------

2

SQL> select instance_number from v$instance;

INSTANCE_NUMBER
---------------
2

SQL>

at this moment piodbserv2 is only on node2. when i kill my user session and try connect again it will connect to node1. but i suspected that after forcibly rellocated service, my sessions will be disconnected from node2 forcibly also.