Fix rfcomm disconnected event not occured issue

Fix rfcomm disconnected event not occured issue

In case rfcomm disconnect operation is done on server side,
disconnected event is not occured on client side because
registration connection and unregistration connection are
different.

If shared connection was in used for registration, shared
connection also should be used for unregistration. Otherwise,
each owner name will be different.

For example,
Owner name of shared connection - :1.219
Owner name of private connection - :1.218

Change-Id: I44a08fda3618f94e674ab09fb189181e720b9226
Signed-off-by: Wootak Jung <wootak.jung@samsung.com>