Hello,
there is a logic inside the component that optimizes the use of servers, and it holds the client connection from the component to the target OPC server longer than the application code requires. This is by design, and helps in situations where the application code may be creating and disposing the objects frequently; if this is passed to the target OPC server, the performance would suffer terribly.
By default, the component holds the connection to the server for 2 minutes, so I assume you simply haven't waited that long to see it happening. You can influence this behavior by manipulating HoldPeriods.TopicRead and .TopicWrite properties of the EasyDAClient. You can set them to lower values or even zero, at the expense on losing some of the optimization described above.
More such settings exist - see e.g. www.opclabs.com/onlinedocs/Qui....
I hope this helps