1. Currently this is a known limitation to the SF connection in integration console.
2. Once a sf env is connected in the integration console, the CTI apps will use the integration console backend to proxy the sf requests. This makes all these requests use the admin's token that was used to connect the env to the integration console.
3. Because now all requests are using the admin's tokne, the tasks created are all created by the admin. Although the service makes an effort make the owner the user who handled the call, but not sure if that works for all cases, especially if the call was logged with AAL instead of with CTI app.

If the customer absolutely needs the tasks to be created by the users, then disconnect the sf env from integration console. That will force the CTI apps to use native CTI interface to create tasks, which will be using each user's session instead. However, that will block them from using AAL.