Yes, once the ticket expires you are no longer authorized to do things, so it will fail.
You have a few options for dealing with this.
If you happen to log into your ansible controller machine using your windows domain username and password (it is possible to use active directory for this) then you will likely have a kerberos ticket as a result of logging in. If you want to use that ticket I think you can just put a @ in the ansible_user name in your windows group vars and ansible will attempt to use the ticket you got when you logged in.
Another way of dealing with it is to wrap ansible in a script that calls kinit before you start running ansible.
I use an ansible connection plugin which acquires the ticket for me and then removes it at the end of each run of ansible or ansible-playbook.
If you are interested in using it, there’s a version of it here https://github.com/ansible/ansible/pull/14972 but its not likely to be ‘the ansible way’ of doing things in future and may need some tweaks to get working.
Also, now that 2.1 is out you can use NTLM instead of kerberos if that is an option for you.
Hope this helps,
Jon