Thank you for the report.  This bug is fixed in the Kerberos 5 release
1.4 betas and will appear in future KFW releases.